fix: preserve selections when config import is invalid - #4994

Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review.

Summary by CodeRabbit

• Bug Fixes
  • Improved configuration imports by validating all selections before applying changes.
  • Invalid or unsupported selections no longer leave the app partially updated.
  • Imported configurations now replace existing selections cleanly.
  • Successful imports consistently reset the related UI state.
• Documentation
  • Added guidance for handling configurations with removed or renamed catalog entries.
• Tests
  • Added coverage for successful imports, invalid configurations, selection preservation, and UI reset behavior.

Walkthrough

Update-WinUtilSelections validates imported selection keys before updating state. Invoke-WPFImpex uses atomic replacement during imports. Tests and documentation cover valid imports, invalid imports, preserved state, and UI reset behavior.

Changes

Selection import state

Estimated code review effort: 3 (Moderate) | ~20 minutes

Merge Risk: ⚪ Minimal · up to 45f90

The import behavior is covered for valid replacement and invalid-import preservation, and no actionable merge-blocking risk remains after normal checks and review.

Sequence Diagram(s)

sequenceDiagram
  participant InvokeWPFImpex
  participant UpdateWinUtilSelections
  participant SelectionState
  InvokeWPFImpex->>UpdateWinUtilSelections: Import flattened selection keys with -Replace
  UpdateWinUtilSelections->>SelectionState: Validate keys and collect typed lists
  UpdateWinUtilSelections->>SelectionState: Replace synchronized selections

Possibly related PRs

• ChrisTitusTech/winutil#4911: Both modify Invoke-WPFImpex.ps1 import handling.
• ChrisTitusTech/winutil#5002: Both modify Update-WinUtilSelections and import-selection behavior.

Suggested labels: bug

Suggested reviewers: christitustech

• X
• Mastodon
• Reddit
• LinkedIn